Exporting CCTs

It is possible to export a CCT and all its associated files such as Script and Stub files and their directory structures, and to package them up into a single ZIP’d archive. This can then be moved between projects or used to aid support when CCT updates are needed.

CCTs are stored in several places and using the export (and import) commands will help to ensure these areas remain consistent. Using the ’-C’ (or --cct-location) specifies where the CCT will be extracted from. Values are:

  • INSTALL: The CCT installation directory, eg

    /home/bill/Helix-QAC-<version>/config/cct

    or

    C:\Perforce\Helix-QAC-<version>\config\cct
  • LOCAL: The CCT directory in the local user data location, eg

    /home/bill/.config/Perforce/Helix-QAC-<version>/config/cct

    or

    C:\%LOCALAPPDATA%\Perforce\Helix-QAC-<version>\config\cct
  • PROJECT: The CCT directory of a project, eg

    /home/bill/sample/configs/Initial/config/cct

    or

    C:\sample\configs\Initial\config\cct
  • USER: Any file or directory specified by the user

The export-file specifies the name of the output file. This is optional and if not specified it is based upon the cct-location parameter:

  • INSTALL: INSTALL.zip_cct
  • LOCAL: LOCAL.zip_cct
  • USER: USER.zip_cct
  • PROJECT: <parent-directory>.zip_cct
Only valid CCTs can be exported. If the CCTs to be exported are invalid (such as missing Stub/Script directories/files etc) then the resultant archive may be incomplete. A non-zero return code will indicate this.